Coping with contradictions in business process re-engineering
نویسندگان
چکیده
Introduction The campaign to improve organizations operates under many banners, including total quality management, continuous improvement, right-sizing, organizational transformation, and so on. The common goal for these approaches is to change how business is conducted in order to improve organizational performance. Since 1990, few treatments of organizational change or improvement have been complete without consideration of business process re-engineering (BPR). BPR's most fervent advocates, Hammer and Champy (1993), have defined it as " the fundamental rethinking and radical redesign of business processes to achieve dramatic improvement in critical, contemporary measures of performance, such as cost, quality, service, and speed ". In their view, BPR promises to transform organizations by fundamentally altering their core processes, thereby achieving radical improvements in performance. Practitioners have responded enthusiastically to BPR, making it the " hottest management concept since the quality movement " (Byrne, 1993). For example, a survey conducted by Deloitte & Touche in 1993 showed that corporate chief information officers were involved in an average of 4.4 re-engineering projects (Hayley et al., 1993). Another survey revealed that as many as 88 per cent of large corporations were engaged in BPR projects and that many others planned to begin projects soon (Bashein et al., 1994). In 1992, the worldwide BPR market was projected to grow at a rate of 46 per cent per year, reaching $2. Thus, re-engineering has quickly become, and remains, a very popular approach to organizational improvement. The preponderance of early writing about BPR appeared in trade and professional journals. While not all of this material was favourable, critical academic perspectives and empirical analyses were noticeably absent [1]. More recently, academics have provided both equivocal empirical evidence and cynical evaluations and analyses of BPR's claims and arguments. European academics have been especially critical, claiming that BPR is not a novel
منابع مشابه
Preparing for Technology-Related Organizational Change An Activity-Theoretical Perspective
ICT-related change is usually studied from the point when a technological artifact has arrived in an organization. Applying an activity-theoretical lens, this paper explores the contradictions within a medium-sized organization’s central activity system, the manifestations of which motivated the decision to engage in a substantial change and shaped the object of the initiative. It illuminates t...
متن کاملمستندسازی گسترده فرایندها در بخش دولت: ارائه یک راهکار
Government is facing numerous problems one of them is the lack of coordination in business processes. However, due to the size of the government, complexities and diversifications processes are hard to document, update and improve. This causes serious inefficiencies in managing the organizations which motivates process improvement and re-engineering. The first step to accomplish this goal is pr...
متن کاملارزیابی تاثیر فنّاوری اطلاعات بر بهره وری در شرکت توزیع برق استان آذربایجان غربی
بهرهوری یکی از مفاهیم مهم اقتصادی است که عبارت از به حداکثر رساندن استفاده از منابع و نیروی انسانی و کاهش هزینههای تولید آنگونه که به سود کارکنان، مدیریت و عموم مصرفکنندگان باشد. یکی از عوامل موثر بر رشد بهرهوری، سرمایهگذاری در بهکارگیری فنّاوری اطلاعات در سازمانها است. بسیاری از اقتصاددانان فناوری اطلاعات و ارتباطات را بهعنوان هسته اصلی تغییرات فنی زمان حاضر میدانند و سعی در کمی کردن ...
متن کاملOptimization of WS-BPEL Workflows through Business Process Re-Engineering Patterns
With the advent of XML-based SOA, WS-BPEL swiftly became a widely accepted standard for modeling business processes. Although SOA is said to embrace the principle of business agility, BPEL process definitions are still manually crafted into their final executable version. While SOA has proven to be a giant leap forward in building flexible IT systems, this static BPEL workflow model should be e...
متن کاملTowards the Proper Integration of Extra-Functional Requirements
In spite of the many achievements in software engineering, proper treatment of extra-functional requirements (also known as non-functional requirements) within the software development process is still a challenge to our discipline. The application of functionality-biased software development methodologies can lead to major contradictions in the joint modelling of functional and extra-functiona...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
برای دانلود متن کامل این مقاله و بیش از 32 میلیون مقاله دیگر ابتدا ثبت نام کنید
ثبت ناماگر عضو سایت هستید لطفا وارد حساب کاربری خود شوید
ورودعنوان ژورنال:
- IT & People
دوره 9 شماره
صفحات -
تاریخ انتشار 1996